home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Univers Interactif 3
/
INTERACTIF.BIN
/
mac
/
Planete.net
/
Internet Confirmés_Vrac
/
HyperWais.sea
/
Release Notes
/
Release Notes 5 Oct 1992
< prev
next >
Wrap
Text File
|
1992-10-29
|
3KB
|
91 lines
Release Notes 5 October 1992
---------------------------
Version 1.4
HyperWais Stack
---------------
- Added a status line to the small stack (just like the
large stack).
- The status line now gets erased when the operation which
filled it with a status message finishes.
- Fixed a couple of syntax errors in some of the scripts.
- Moved the handlers which deal with adding a source to
the sources field and parses a source file to the background
script because space was getting to be an issue in the
stack script.
- Minimum memory requirements for the stacks mean that
Hypercard has to have at least 1500K allocated to it in the
Get Info window. When the stack is opened, it will check to
see if it has at least of free space, if not it will say so but
not stop the user from using it.
XFCNs
-----
- The memory management in the XFCN functions has been
improved in that low memory situations are handled more
gracefully. The XFCN functions now allocate all the memory
they will need before calling the wais caller routines, and
return an error if any of the allocations fail for any reason.
This was not a problem with previous versions of the XFCN
functions as most, if not all, of the time, sufficient memory
was available.
- There is a place where memory management could be a
problem and that is in the HCUtils.c functions. Some of these
functions allocate memory without verifying that the
allocation was successful. This may not be a problem because
the allocations are really small (in the order of 10 to 30 bytes).
If Hypercard gets into a situation when we cannot allocate
a 30 bytes handle, then we really are in trouble.
Wais Caller routines
------------------
- The memory management in the wais caller functions has been
improved in that low memory situations are handled more
gracefully. The functions now allocate all the memory they will
need before sending out the Apple Event, and return an error
if any of the allocations fail for any reason. This was not a
problem with previous versions of the wais caller functions
as most, if not all, of the time sufficient memory was
available.
Wais Listener and C Libraries
--------------------------
- The listener will now concatenate the document types returned
by the server in the document headline. The list can be up to
16 characters long (including terminating nulls) and is '\r'
delimited.
- The Apple Event handles has been improved to deal gracefully
with low memory situations. The change means that if memory
cannot be allocated, the Wais Listener will tell the caller about it, rather than perform the requested operation with bad
pointers/handles. The scheme is as follows:
- allocate all the memory we will requires, if this fails
return an error to the client.
- execute the requested operation.
- return any error and results.
- dispose of all allocated memory.
This was not a problem with previous versions of the Wais
Listener because the memory allocated was sufficient to the
extent it would not run out of memory.
- Fixed an interesting bug which caused us to loose one
byte out of every document chunk we got back from the server.
This bug got into the system because the wais server is off
by one byte when it reports that a document chunk has been
downloaded. This was not really noticable with textual documents
but really trashed pictures.